close() callback hangs again

Having another problem in another script with the close() hanging.
Different issue than in my prior post here:
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=363294

Specifically, one dialog (dbMain) has a button that puts up a new dialog (dbNew).
For dbNew, I have two buttons:
ok(dbNew,okCallback) and
close(dbNew,false,closeCallback) (button not visible, but standard Windows "X" icon will invoke)
Both callbacks simply set some flags and nothing more.
The dbMain button callback that puts up this 2nd (dbNew) dialog simply:
blocks on dbNew; then unconditionally releases/hides/destroys dbNew.

Problem is: ok button works to close dbNew and go back to dbMain, but the "X" icon in top right (for close), doesn't do anything. How do I make that "X" functional??

If I change the close() callback to be same function as for ok(), the result is the same ("X" icon doesn't do anything).

If I add a call to hide() in the close callback like the Help suggests, this hangs doors (new dialog goes invisible, other dialog/DOORS items non-functional/non-responsive, if they are even visible).

Thanks,
strathglass.
strathglass - Fri Mar 25 10:40:50 EDT 2011

Re: close() callback hangs again
Mathias Mamsch - Fri Mar 25 12:09:57 EDT 2011

• Always do a release if you do a block. I always do: block dbVar; release dbVar, in callbacks I only do "hide dbVar"
• Don't call destroy in a callback, call it after the block.

Re: close() callback hangs again
llandale - Fri Mar 25 14:55:04 EDT 2011

This would be a lot easier if you posted the relevant code. But I can infer reasonably well, so here goes: your 2nd dialog is "blocked" and your "close" fails to "release" it.

Your DB main callback that "blocks" dbNew does not "release" it; "release" is how you close the dialog from the new callbacks and get DXL to start executing the statement after the "block". After "block", you should "destroy". However, having an extraneous "release" after "block" doesn't seem to matter.

I wonder if you have two "closeCallback" functions; would it not be easier to understand if you renamed this one to "dbNew_CloseCallback"?

Blocked code should look like this:

void  clbkClose(DB dbXX)
{  DoWhatever
   release(dbXX)
}
void  buttonWhatever(DB dbXX)
{  do whatever
   sometimes call clbkClose(dbXX)
}
void  CreateDialog()
{
    create the dialog
    close(db, false or true, clbkClose)
    block(db)
    destroy(db)
    proceed.
}

• Louie

Re: close() callback hangs again
strathglass - Mon Mar 28 07:25:32 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:25:53 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:26:08 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:26:44 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:27:19 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:28:56 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:31:42 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:32:34 EDT 2011

Re: close() callback hangs again
strathglass - Mon Mar 28 07:33:54 EDT 2011

Re: close() callback hangs again
llandale - Mon Mar 28 14:26:08 EDT 2011

• Louie